x86/32on64: properly honor add-to-physmap-batch's size
authorJan Beulich <jbeulich@suse.com>
Wed, 26 Apr 2017 07:48:45 +0000 (09:48 +0200)
committerJan Beulich <jbeulich@suse.com>
Wed, 26 Apr 2017 07:48:45 +0000 (09:48 +0200)
commit144aec4140515c53bb1676df71a469f3e285c557
treec5040d83465365082a319fbebdff01b8b75ef9b8
parent9182835740ac37cf5295b15eb47058f39fc14c8f
x86/32on64: properly honor add-to-physmap-batch's size

Commit 407a3c00ff ("compat/memory: fix build with old gcc") "fixed" a
build issue by switching to the use of uninitialized data. Due to
- the bounding of the uninitialized data item
- the accessed area being outside of Xen space
- arguments being properly verified by the native hypercall function
this is not a security issue.

Reported-by: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com>
Signed-off-by: Jan Beulich <jbeulich@suse.com>
Reviewed-by: Wei Liu <wei.liu2@citrix.com>
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
Release-acked-by: Julien Grall <julien.grall@arm.com>
xen/common/compat/memory.c